home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / catD / init.z / init
Encoding:
Text File  |  1998-10-30  |  4.8 KB  |  133 lines
  1.  
  2.  
  3.  
  4. iiiinnnniiiitttt((((DDDD2222))))                                                              iiiinnnniiiitttt((((DDDD2222))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      init,edtinit,start - initialize drivers and their devices
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _vvvv_oooo_iiii_dddd _p_r_e_f_i_x_iiii_nnnn_iiii_tttt_((((_vvvv_oooo_iiii_dddd_))))_;;;;
  13.      _vvvv_oooo_iiii_dddd _p_r_e_f_i_x_eeee_dddd_tttt_iiii_nnnn_iiii_tttt_((((_ssss_tttt_rrrr_uuuu_cccc_tttt _eeee_dddd_tttt _****_))))_;;;;
  14.      _vvvv_oooo_iiii_dddd _p_r_e_f_i_x_ssss_tttt_aaaa_rrrr_tttt_((((_vvvv_oooo_iiii_dddd_))))_;;;;
  15.  
  16. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  17.      The _iiii_nnnn_iiii_tttt, _eeee_dddd_tttt_iiii_nnnn_iiii_tttt and _ssss_tttt_aaaa_rrrr_tttt routines execute during system initialization
  18.      to initialize drivers and the devices they control.
  19.  
  20.    RRRReeeettttuuuurrrrnnnn VVVVaaaalllluuuueeeessss
  21.      None
  22.  
  23. UUUUSSSSAAAAGGGGEEEE
  24.      These entry points are optional.
  25.  
  26.      Although _iiii_nnnn_iiii_tttt, _eeee_dddd_tttt_iiii_nnnn_iiii_tttt and _ssss_tttt_aaaa_rrrr_tttt routines all perform initialization
  27.      tasks, they execute at different times during system start-up.  For this
  28.      reason, they should be used to handle different types of initialization
  29.      tasks.  All of these routines are called after interrupts have been
  30.      enabled.
  31.  
  32.      _iiii_nnnn_iiii_tttt routines:
  33.  
  34.           execute during system initialization
  35.  
  36.           handle any driver and device setup and initialization that must take
  37.           place before I/O is initialized
  38.  
  39.           typically perform tasks such as: inititalize semaphores and locks,
  40.           malloc memory for driver data structures, initialize driver data
  41.           structures, etc.
  42.  
  43.      _eeee_dddd_tttt_iiii_nnnn_iiii_tttt routines:
  44.  
  45.           exist for drivers that use VECTOR lines in the _ssss_yyyy_ssss_tttt_eeee_mmmm(4) file
  46.  
  47.           are executed immediately after the _iiii_nnnn_iiii_tttt routines
  48.  
  49.           may be called multiple times per driver, once for each controller
  50.  
  51.           probe the given device and perform device specific initialization
  52.  
  53.      _ssss_tttt_aaaa_rrrr_tttt routines:
  54.  
  55.           execute after all I/O and  system services are initialized
  56.  
  57.           handle all driver and device setup and initialization that can take
  58.           place after system services are initialized (most driver setup and
  59.           initialization tasks can be performed at this time, using a _ssss_tttt_aaaa_rrrr_tttt
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. iiiinnnniiiitttt((((DDDD2222))))                                                              iiiinnnniiiitttt((((DDDD2222))))
  71.  
  72.  
  73.  
  74.           routine)
  75.  
  76.           handle any driver and device setup and initialization that can only
  77.           take place after system services are initialized
  78.  
  79.      _iiii_nnnn_iiii_tttt, _eeee_dddd_tttt_iiii_nnnn_iiii_tttt and _ssss_tttt_aaaa_rrrr_tttt routines for dynamically loadable modules are not
  80.      called during system start-up as they are for statically linked modules.
  81.      A loadable module's initialization is called each time the module is
  82.      loaded into a running system.
  83.  
  84.    SSSSyyyynnnncccchhhhrrrroooonnnniiiizzzzaaaattttiiiioooonnnn CCCCoooonnnnssssttttrrrraaaaiiiinnnnttttssss
  85.      Functions that can result in the caller sleeping, or that require user
  86.      context, such as _ssss_llll_eeee_eeee_pppp(D3), may not be called from _iiii_nnnn_iiii_tttt, _eeee_dddd_tttt_iiii_nnnn_iiii_tttt or
  87.      _ssss_tttt_aaaa_rrrr_tttt.  Any function that provides a flag to prevent it from sleeping
  88.      must be called such that the function does not sleep.
  89.  
  90. RRRREEEEFFFFEEEERRRREEEENNNNCCCCEEEESSSS
  91.      _ssss_tttt_aaaa_rrrr_tttt(D2)
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.